Update .mergify.yml #104
Merged
Update .mergify.yml #104
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
An example of PR that "should" have been merged, but wasn't is #94. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Not entirely sure why, but scala-steward does not always put the label
early-semver-patchon PRs when they are patch releases. However, it does seem to putsemver-spec-patchon all path releases. Further, this is the label that is used by the creator of scala-steward as seen here: https://github.com/fthomas/refined/blob/master/.mergify.yml. There isn't any documentation that I can find regarding when different labels appear or don't appear, but this seems like a good indicator that we can rely onearly-semver-patch